Beta 2 of Gravity Forms v1.8 is now available. Beta 2 features new features, minor enhancements and bug fixes to Gravity Forms, the Add-On Framework and the API.
Gravity Forms v1.8 is a major update that introduces a lot of great new user features, enhancements, and powerful new developer features such as the new Add-On Framework and a complete API. You can get complete details on all of the great new features and enhancements by reading the Gravity Forms v1.8 Beta 1 release announcement.
Please report any bugs or issues you may encounter to our support team and make it clear it is in reference to the Gravity Forms v1.8 Beta 2 release when doing so.
If you are currently using the Beta 1 release, you will need to manually update your install in order to install Beta 2. We highly recommend all beta testers do so.
We will be releasing v1.8 via automatic upgrade once it has undergone beta testing to our satisfaction. Own Gravity Forms and want to take it for a spin and help us test out the new features? Grab a copy on the downloads page!
Please Note: This is a beta release and as such you should use at your own risk. We are still actively working on UI enhancements and refinements for the final public release. Gravity Forms 1.8 requires WordPress 3.7+.
Documentation for the features and functionality in Gravity Forms v1.8 is still in progress. The Gravity Forms documentation as a whole is being completely overhauled and will launch with the final release of Gravity Forms v1.8. Please be patient as we completely overhaul our documentation from the ground up. However, documentation does exist for the new Add-On Framework as well as the new API.
Here is a rundown of what is new in Gravity Forms v1.8 Beta 2...
Gravity Forms
- Added multifile support to the 'post custom field' field (file upload field type).
- Added Entry ID, Entry Date, Starred, IP Address, Source URL, Payment Status, Payment Date, Payment Amount, Transaction ID and User to the list of available fields in the entry list search, export conditional logic and Add-On Framework results page filter.
- Added sorting by active/inactive in form list.
- Added form-specific version of "gform_register_init_scripts" hook.
- Added JS filter: "gform_spinner_url" to allow modifying the spinner URL with the new gformInitSpinner() function.
- Added logging statements to GFFormsModel::create_post().
- Added logging statements to GFAsyncUpload::upload().
- Updated gformInitSpinner() to be generic and moved to gravityforms.js.
- Updated enqueue and print script functions to enqueue gravityforms.js when AJAX is enabled.
- Updated confirmation and notification titles to link to edit view for that item.
- Updated the help page: removed references to the forum.
- Updated the field filters on the export entries page and results page to include greater than and less than operators by default.
- Moved the QR Code library to the includes folder so it can be reused more easily.
- Fixed element IDs for the date field.
- Fixed search criteria operators for likert fields.
- Fixed an issue with the field filter drop down which could result in duplicate inputs.
- Fixed issue with the field filters where the mode is added more than once.
- Fixed issue where datepicker was displaying below WP content.
- Fixed issue where notification edit page was "busting out" of the WP wrapper.
- Fixed the styles for the active/inactive column of the notification list and confirmation list.
- Fixed the styles for the field header in the form editor in Chrome.
- Fixed issue with ReCAPTCHA field throwing Javascript error.
- Fixed an issue with multi-file uploader opening multiple file dialogs.
- Fixed issue with calculation formatting.
- Fixed an issue with the multi-file uploader in IE8.
- Fixed an issue with the multi-file uploader for forms with conditional logic in IE.
- Fixed tabindex for AJAX enabled forms after validation.
- Fixed validation of standard phone field when value is zero.
- Fixed issue where no formatting was being applied to calculated results.
- Fixed issue where
Oops! We could not locate your form.
shortcode (plural) was not detected and scripts were not loading correctly. - Fixed bulk actions at the bottom of the form list to reflect recent changes.
Gravity Forms Add-On Framework
- All scripts and styles are now always registered so they can be used as dependencies.
- Added support for storing previous settings when saving new settings.
- Added support for plugin_settings_title() overridable function.
- Added "feedName" as default column and field setting for payment add-on.
- Added add_field_before() and add_field_after() functions to facilitate adding new fields to existing field groups.
- Added support for 'style', 'class', and 'id' properties to $sections.
- Added feed_settings_title() method to Feed Add-on rather; used as title of feed detail page.
- Added further details to some error messages.
- Renamed has_feed_for_this_addon() method to has_feed().
- Updated rgempty() function to support passing just an array for empty() validation.
- Updated setting_dependency_met() method to handle when false value is passed as $dependency.
- Updated setting validation to not validate settings where dependency is not met.
- Updated all calls to $_short_title to use get_short_title().
- Removed some inline styles and added to admin.css.
- Updated section title markup to use H4 and match styles of GF Form Settings.
- Updated get_setting() function to support a $settings parameter.
- Updated Payment Add-on fields to be grouped by their dependencies (based on transaction type).
- Updated feed_callback icon to use font.
- Updated error icon to use fontawesome.
- Fixed results filter mode initialization.
Gravity Forms API
- Updated Web API slug from gfwebapi to gravityformsapi.
- Updated the API Functions to remove the capability checks.
- Updated the Web API to respond always with a 200 HTTP status along with a JSON object containing the status code and response.
- Fixed an issue with sorting entries from the API.
Will v1.8 support activation and configuration at the network level? Currently, even when activated at the network level, Gravity Forms must be configured on each individual subsite (including entry of the serial) before it works.
Gravity Forms already supports WordPress Multi-Site and can be network activated. You can also configure your WordPress Multi-Site setup so that the license key is automatically applied on any new site that is created on the multi-site (note it only occurs when a new site is created). This is done by adding an option to your wp-config.php file which contains your license key. You can find documentation on that here:
http://www.gravityhelp.com/documentation/page/WP_Config_Options
Other than that, each site on a multi-site behaves as it's own WordPress site and therefore Gravity Forms behaves as an individual install. So forms, entries, etc. are all going to be associated with the individual site because that is how WordPress Multi-Site works. Each site in a Multi-Site gets it's own database tables, not only for Gravity Forms related data, but also Posts, etc. within WordPress.
I tried the v1.8 Beta 1 and it worked fine for me.
I was most interested in the possibility to limit the file size of uploaded files.
Unfortunately this works only with the "file upload" field and not with the "post image" field.
I use GF on a casting/model agency site where users create posts by filling in a form and upload images through the same form. This works fine, were it not for the fact that users often try ti post images that are far too big, resulting in errors.
If the new GF version could put a limit on the "post image" field too, just like the "file upload" field that would be extremely useful.
Post Creation, including the Post Image field, will be getting a complete overhaul which is currently planned for the v1.9 release. At that point it will support this functionality as it will use the same File Upload field. Post Creation as a whole will be overhauled from the ground up making it much more powerful and flexible.
Hi guys,
i was hoping for a quick fix for the telephone international setting. It is still possible to insert letters instead of just numbers. Is this on the list for the upcoming update?
I'm not aware of any plans for updating the Telephone Field to support alpha-numeric characters instead of just numbers. None of the other major form builder solutions i've tested support alpha-numeric characters in phone number fields, including international phone fields as they are usually always numeric. People sometimes advertise phone numbers using letters but those letters correspond to numbers on the phone itself. Do you know of any standards that we can look at that show international locales that support alpha-numeric phone numbers so we could look into this further? The alternative is to simply use the Single Text field and then you could also implement a javascript mask using the mask option.
Hi
Have tried the API wrapper, and it works as you've written it. However, it doesn't quite fit my requirements.
I need to either POST the get_*() calls, or be allowed to add to $query in send_request() somehow. Wouldn't be against having a bit of both.
Any plans to add those, or will I have to do lots of copy pasta?
I am going to forward your comment over to one of our lead developers and he will be replying via email regarding your API question.
http://wordpress.org/plugins/gravity-forms-wysiwyg/ is still the way to get a WYSIWYG field for 1.8?
Currently that 3rd party Add-On or a customization via hooks is the only way. But I will get it added to the v1.9 roadmap. It's a simple enough update and with WordPress core changes things the editor is much easier to implement so it's something that has just been on the back burner for us. We typically try not to step on 3rd party Add-On toes, but this is a pretty minor one.